home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group94b.txt
/
000043_icon-group-sender _Mon Sep 5 17:10:07 1994.msg
< prev
next >
Wrap
Internet Message Format
|
1995-02-09
|
1KB
Received: by cheltenham.cs.arizona.edu; Mon, 5 Sep 1994 16:06:04 MST
Date: Mon, 5 Sep 1994 17:10:07 +0600
From: jeffery@runner.jpl.utsa.edu (Clinton L. Jeffery)
Message-Id: <9409052210.AA14549@runner.utsa.edu>
To: espie@basilic.ens.fr
Cc: icon-group@cs.arizona.edu
In-Reply-To: <34ditv$nec@nef.ens.fr> (espie@basilic.ens.fr)
Subject: Re: Icon - still alive??
Content-Length: 781
Errors-To: icon-group-errors@cs.arizona.edu
Marc Espie writes, concerning Icon's new loadfunc() facility for
calling C routines:
> How many architectures does that new call work under ? Not too many I
> think...A perfect example of how general and elegant that mechanism is :-(
> (I'd like it to work on every machine myself).
My impression is that loadfunc() is delightfully general and elegant. The
fact that the first platforms for which it is implemented are certain
flavors of UNIX is a side-issue. As always, it will be up to implementors
on various platforms to see if they can add loadfunc() to their version of
Icon. The reason I am happy about loadfunc() is that it appears a broad
class of common systems *will* be able to support it once someone reasonably
gifted sets out to do loadfunc() for each system.